Add guide on which genders to target and communication. #90
Conversation
application_form/target.md
Outdated
|
|
||
| ## A brief introduction to gender | ||
|
|
||
| A lot of people are assigned a gender at birth, and continue to identify with that gender - they feel fine about it. These people are called cisgender (or cis women/men). Some people are transgender, which means they do not identify with that gender. Most of these people have been assigned female at birth (AFAB) or assigned male at birth (AMAB), . |
There was a problem hiding this comment.
Is there something missing at the end of this sentence? The comma is weird.
application_form/target.md
Outdated
|
|
||
| - Early on in your event page, clarify your target group as: “women and non-binary people (regardless of gender expression or assigned gender at birth)” | ||
| - Consistently using “women and non-binary people” everywhere, and never “women” alone. | ||
| - Ask for people’s pronouns in the application form - this target group means you can’t assume "she" as the default pronoun. If you make name badges, try to print the pronouns on them. |
There was a problem hiding this comment.
I have mixed feelings about printing pronouns on name badges (or forcing everybody to do it, or at least to the degree where it would be unusual not to do so). I write my pronouns on badges, and know other people who do.
But it’s very unusual to have my pronouns confused, so the risk to me is minimal. And people who are openly trans/non-binary do the same – the same pronouns you might see on a Twitter profile. I wonder if everybody is comfortable doing this?
e.g. if you’re non-binary but aren’t out to everyone, do you put they/them pronouns (thus outing yourself), or put pronouns you’re not comfortable with?
Disclaimer: cis man who currently has no issues with the pronouns people who use for him, so I may be talking nonsense.
There was a problem hiding this comment.
I've added the suggestion to make this question optional.
application_form/target.md
Outdated
| - Woman | ||
| - Non-binary/other gender | ||
|
|
||
| This allows you to assume that people who answer "man" are cisgender men, and allows you to prioritise other applications over these. |
There was a problem hiding this comment.
Is that true? If presented with these options, I’d expect at least some trans men to pick the answer “Man”.
There was a problem hiding this comment.
Yes, entirely right. I've clarified this a bit. The issue is that if you include trans men in your target group, you'd have to ask for "men" and "trans men" separately, but usually I'd suggest not adding separate options for trans if not needed - trans women are women, after all.
application_form/README.md
Outdated
| @@ -1,6 +1,6 @@ | |||
| # Application process | |||
|
|
|||
| **The goal of Django Girls is to bring new people into technology, especially women. You're free to organize a mixed-gender groups for your event but women must have priority when applying.** | |||
| **The goal of Django Girls is to bring new people into technology, especially women. You're free to organize a mixed-gender groups for your event but women (and non-binary people and/or trans men, if included) must have priority over (cisgender) men when applying. See [Who to target](./target.md) for suggestions on this.** | |||
There was a problem hiding this comment.
- Break down to 2 sentences to avoid over-use of parantheses
- Flip sentence with "for more info" so that the link is last and the reason to click the link is written so
application_form/target.md
Outdated
| @@ -0,0 +1,57 @@ | |||
| # Who to target? | |||
|
|
|||
| Django Girls events can have different target groups in terms of gender. This is your choice, but the most important is to understand your own choice and be explicit and consistent in your communication. The basic options come down to: | |||
There was a problem hiding this comment.
basic options > the workshop scope can be targeted for:
application_form/target.md
Outdated
|
|
||
| Opening up applications to women, including trans women, is a common choice for Django Girls events. The website defaults to this, but we recommend adding an explicit mention of being trans inclusive. A good way to word this is: | ||
|
|
||
| > We are trans-inclusive and welcome applications from all women. |
There was a problem hiding this comment.
all people who identify as women
application_form/target.md
Outdated
|
|
||
| The examples listed above do not include trans men (people assigned female at birth, transitioned to men). In their past, these people may also have experienced difficulties in entering technology similar to those of women. If you would like to include this group, you could expand your wording to: | ||
|
|
||
| > women, non-binary people and trans men (regardless of gender expression or assigned gender at birth) |
There was a problem hiding this comment.
oxford comma before "and trans men"
There was a problem hiding this comment.
maybe replace the parantheses with a comma
mxsasha
changed the title
|
I believe this PR is now ready for a review by Django Girls committers to be considered for merging. |
This PR adds a guide on which genders organisers could target, and guidelines on how to communicate this in a Django Girls event.
General rationale for this update is provided in the added document. The approach I've tried to take is not to push people to make a particular choice, but rather to help organisers understand their options, understand the choice they take, and to communicate this choice clearly. I think this is needed, because I've seen organisers struggle with this a number of times, in a way that hurts the goals they had with their workshop.
I'm aware that this creates a small policy change in the DG requirements, as it allows a bit more room in the requirement that women must be prioritised. However, I feel this is appropriate if seeing DG workshops as events that can be set up to help gender minorities, rather than always exclusively women. But this remains an organiser choice.